Last week we flew from Helsinki to Belgium with a fourship formation, the lead was doing the navigation and had garmin 430 GPS on board. We however did not and I was following with skydemon in VFR mode. At some point the ATC cleared us to OGLOB waypoint and we turned with the lead but I could not find this point. First of all I hadnt understood well the controller and I tried using the search waypoint function in skydemon. Upon typing O some waypoints appeared. Then I entered the G and skydemon says : No Results found !!!!
Only when typing it fully it finds this point. Is this normal? Should this waypoint not show already when typing OG or OGL ...

In the mean time I have also switched on to see the airways waypoints on the map and that makes it easier to spot the waypoints but the behavior of the search function is still the same.

Greetz Peter

We can't really do anything that would slow down searches. With a lot of charts loaded, searching is already slow enough on some devices.
Because you were looking for a five-letter designated point, we do require the whole point to be typed before they are included in the search. In this case an exact match is required, again for performance reasons.

Mabe the user could somehow specify that he is going to perform a search on a five letter ID. That would narrow down the pool and you could probably do it on the fly. I am not a database expert but there ought to be a way to structure indices cleverly to speed up the search. How about letting the user specify a search region such as a radius from current position or country?

Otherwise it is nigh impossible to find a waypoint you know starts with O but couldn't quite make out phonetically over the radio.

-- Chris.